• feat: add Stainless SDK config and misc cleanups #132
• feat: rename Error to GridError and add additionalProperties to error schemas #131 👈 (View in Graphite)
• feat: add Customer API discriminators and consolidate customer changes #130
• feat: add Quote/Transaction discriminators and remove inline examples #129
• feat: add isPlatformAccount to PaymentInstructions and remove PaymentAccountOrWalletInfo refs #128
• feat: rename accounts to data in list external accounts response #127
• feat: convert single-value enums to const for base types #126
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Greptile Overview

Greptile Summary

This PR introduces a new GridError schema and standardizes error handling across the API specification by adding additionalProperties: true to error details objects.

Key Changes:

• Created GridError schema with flexible error details via additionalProperties: true
• Updated all HTTP error schemas (400, 401, 403, 404, 409, 412, 424, 500, 501) to allow additional properties in details objects
• Refactored BulkCustomerImportErrorEntry to extend GridError using composition instead of nested error structure
• Updated webhook response schemas (IncomingPaymentWebhookForbiddenResponse and IncomingPaymentWebhookUnprocessableResponse) to reference GridError

Architecture Improvement:
The change from nested error objects to composition via allOf in BulkCustomerImportErrorEntry improves schema reusability and maintains consistency across error responses. The addition of additionalProperties: true provides flexibility for including custom error metadata while maintaining a consistent error structure.

Minor Issue:
One reference to the old Error schema remains in openapi/paths/customers/customers_{customerId}.yaml for the 410 response. While this doesn't break functionality since Error.yaml still exists, updating it to GridError.yaml would ensure complete consistency across all error responses.

Confidence Score: 4/5

• This PR is safe to merge with minimal risk - changes are well-structured and backward compatible
• The changes are straightforward schema updates that improve error handling flexibility. The new GridError schema and additionalProperties: true additions are backward compatible since they only make the schema more permissive. The refactoring of BulkCustomerImportErrorEntry improves maintainability. One minor inconsistency exists with the 410 error response still using the old Error schema, but this doesn't introduce any breaking changes since both schemas are functionally similar and Error.yaml remains in the codebase.
• openapi/paths/customers/customers_{customerId}.yaml has one outdated schema reference that should be updated for consistency

sequenceDiagram
    participant API as Grid API
    participant Client as API Client
    participant Schema as Error Schema
    
    Note over API,Schema: Error Response Flow
    
    Client->>API: Request with potential error
    API->>Schema: Generate error response
    
    alt Using GridError (new)
        Schema->>Schema: Create GridError object
        Schema->>Schema: Add code, message
        Schema->>Schema: Add details (additionalProperties: true)
        Schema->>API: Return GridError
    else Using Error4xx/5xx (updated)
        Schema->>Schema: Create specific Error object
        Schema->>Schema: Add status, code, message
        Schema->>Schema: Add details (additionalProperties: true)
        Schema->>API: Return specific Error
    else Using BulkCustomerImportErrorEntry
        Schema->>Schema: Extend GridError via allOf
        Schema->>Schema: Add correlationId field
        Schema->>API: Return enriched error
    end
    
    API->>Client: Return error response with flexible details